Component org.nuxeo.ecm.core.automation.core.properties

Resolution Order

The resolution order represents the order in which this component has been resolved by the Nuxeo Runtime framework.
You can influence this order by adding "require" tags in your component declaration, to make sure it is resolved after another component.

Contributions

org.nuxeo.ecm.core.automation.core.properties--configuration

XML Source

<?xml version="1.0"?>
<component name="org.nuxeo.ecm.core.automation.core.properties" version="1.0.0">

  <extension target="org.nuxeo.runtime.ConfigurationService" point="configuration">

    <documentation>
      This contribution is the default contribution for automation properties.

      Here are more details about some of them:
      <ul>
        <li>
          <strong>nuxeo.automation.properties.value.trim</strong>: properties are expected to be of the form "key=value". You may wish to trim the potential spaces around value (e.g.: "key = value", will result in "value" and not " value").
        </li>
        <li>
          <strong>nuxeo.automation.export.aliases</strong>: if true, add an operation documentation for each alias of a given operation.
          Mainly to be backward compatible with old Java Automation client.
        </li>
        <li>
          <strong>nuxeo.automation.allowVirtualUser</strong>: define whether virtual user (non-existent user) is allowed
          in Nuxeo automation. If allowed, Nuxeo server will not check the user existence during automation execution.
          Set this property to true if you use Nuxeo computed user or computed group.
        </li>
      </ul>

      @since 8.2
    </documentation>

    <property name="nuxeo.automation.properties.value.trim">false</property>

    <property name="nuxeo.automation.export.aliases">false</property>

    <property name="nuxeo.automation.allowVirtualUser">false</property>

  </extension>

</component>